This is a comment left during a code review.
Path: test/bench-format-render.test.ts
Line: 34

Comment:
**`as never` bypasses type safety**

`as never` is an unusual cast used here (and on line 41) to silence TypeScript without providing a typed fixture. the project anti-pattern list explicitly forbids `as any`, `@ts-ignore`, and `@ts-expect-error` as type escapes. `as never` achieves the same bypass: asserting the value is `never` makes it assignable to any function parameter.

since `render.mjs` is untyped `.mjs`, the cleanest fix is to cast through `unknown`:

```suggestion
		const markdown = buildMarkdownReport(summary as unknown as Parameters<typeof buildMarkdownReport>[0]);
```

or define a minimal local `BenchmarkSummary` interface and type `summary` against it — either approach avoids the implicit-any pattern the codebase bans.

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: test/bench-format-render.test.ts
Line: 33-47

Comment:
**failures branch not covered**

`buildMarkdownReport` has a distinct code path when `summary.failures.length > 0` (renders `## Failures` section, also has a separate truncation branch at >20 entries). the fixture hardcodes `failures: []` so neither branch is exercised.

given the project's 80% coverage threshold, consider adding one more `it` to cover the failures path:

```ts
it("includes failures section when failures present", () => {
  const withFailures = {
    ...summary,
    failures: [
      { modelId: "gpt-5-codex", mode: "patch", taskId: "task-1", phase: "run", reason: "timeout" },
    ],
  };
  const markdown = buildMarkdownReport(withFailures as never);
  expect(markdown).toContain("## Failures");
  expect(markdown).toContain("timeout");
});
```

this also exercises the graceful `undefined`-mode handling inside the leaderboard builder, which is only reachable with real failure-tagged rows.

How can I resolve this? If you propose a fix, please make it concise.